Exhausting Memory Size

If your LIS file tells you that you've used 65501 words of memory out of 65501 then you have reached the maximum file `size' that LATEX will permit. Unless you've made some error, such as having a file input itself, your choices are to enlarge TEX (this requires a `wizard', whatever that is), make your program smaller, or break your document up into smaller pieces. The last option would be irritating if, for instance, you were writing a book and had to continually keep track of cross-references between these divisions, page numbering and so forth. LATEX uses the include facility to alleviate the tedium. The only drawback is that after a break in the document the new position will begin on a fresh page. Individual Feynman diagrams cannot be broken up this way and this limits their ultimate complexity.

To process just a portion of a document place the different portions in a series of files and have a driving file which includes the statements 

\include <file1> \include <file2> \include <file3>... \include <file n>
These should appear at the positions in which you want them and may be interspersed with text and commands within the driving file. Prior to TEXing the file the commands includeonly <file> should appear for each piece that you want processed on that particular run. For instance, to print out the first part of chapter three of this manual I have a file, which I call FD3A.TEX, containing 
\documentstyle[11pt]{report}
\input FEYNMAN
\includeonly{FEYNMANDOC3A}
\input FEYNMANDOC.INC
where the file FEYNMANDOC.INC, unconditionally input, contains 
\textheight 700pt \textwidth 450pt
<VARIOUS DEFINITIONS COMMON TO ALL PARTS>

\begin{document}           % End of preamble and beginning of text.

\include{FEYNMANDOCTITLE}
\include{FEYNMANDOCPRELIMS}
\include{FEYNMANDOC1}
\include{FEYNMANDOC2A}
\include{FEYNMANDOC2B}
\include{FEYNMANDOC2C}
                     .
                     .
                     .
\include{FEYNMANDOC4H}
\include{FEYNMANDOC4I}
\include{FEYNMANDOC4J}
\include{FEYNMANDOCEXER}
\include{FEYNMANDOCAPPB}
\include{FEYNMANDOCAPPC}
\end{document}
When executed each section will create a number of files such as the <filename>.AUX file. These must be retained on your TEX directory as they transmit information about one section to the others. AUX files tell about page numbering, sections , BIB files contain the accumulated bibliography, TOC files the table of contents and so forth. For this reason it may take several runs to get your document to come out correctly as each AUX file will be updating itself based upon updates of the other AUX files. TOC files will be the last to come out correctly. To print out this entire document I had a COMMAND file called MAKEDOC.COM which contained: 
$ SET DEFAULT DRA1:[LEVINE.TEXBOOK]
$ LATEXIT FDTITLE
$ LATEXIT FDPRE
$ LATEXIT FD1
$ LATEXIT FD2A
$ LATEXIT FD2B
$ PURGE FD*.AUX
$ LATEXIT FD2C
       .
       .
       .
$ LATEXIT FD4H
$ LATEXIT FD4I
$ LATEXIT FD4J
$ PURGE FD*.AUX
$ LATEXIT FDADDA
$ LATEXIT FDAPPB
$ LATEXIT FDAPPC
$ PURGE FD*.*
$ PURGE FEYNMANDOC*.*
Where LATEXIT is a command which LATEXs a file, sends it to the printer and then erases the LIS and printer files. The files FD1, FD2A are like the small FD3A file above which processed just the first part of chapter three. The PURGE statements remove old versions of the AUX files from your disk. The above file is sent as a batch job by a command file like PRINTDOC which contains 
$!  Prints FEYNMANDOC.TEX...all of it.
$ SET DEFAULT DRA1:[LEVINE.TEXBOOK]
$ SUBMIT/NOPRINTER/NOTIFY DRA1:[LEVINE.TEXBOOK]MAKEDOC.COM
The above is in VAX code but the format on other machines should be apparent. This work was supported by the UK Science and Engineering Research Council. I would like to thank all of the people at the Cavendish Labs, Cambridge, England, who gave their preferences and comments as to which line styles should be incorporated.

Michael Levine, 1988